AFP Engage! User's Guide

Troubleshooting

This chapter discusses common problems and their solutions, for both AFP server browsing and AFP URL processing.

AFP Server Browsing

An AFP server targeted by ShareWay IP is not visible in AFP Engage's "Browse AFP Servers" window.

• Be sure that the ShareWay IP machine is running Mac OS 8.5
  
  
• Be sure the SLP plug-in is enabled through the extensions manager on both the AFP Engage! and ShareWay IP machines
  
  
• Be sure you are running ShareWay IP 2.0 or later
  
  
• Double-check the name of the server in the File Sharing control panel on the server machine
  
  
• Perhaps the ShareWay IP machine is not on your subnet and IP multicast is not enabled in your routers. See As an AFP Browser and Open Door's white paper for limitations with SLP
  
  
• Be sure both the target server and ShareWay IP are both active.
  
  
• AFP Engage! will not list servers targeted by a copy of ShareWay IP running on the same machine as AFP Engage!, since such servers cannot be mounted from that machine.

I try to access a server listed in the "Browse AFP Servers" window, but I get a message that the server is not responding.

• The server may no longer be available. When ShareWay deregisters there may be a delay before it is removed from AFP Engage's list.
  
  
• If ShareWay IP Standard Edition targets a server on another machine, it will register with SLP even if the target server is not available. Check that the target server is actually running.
  
  
• There is a bug in the SLP plug-in which ships with Mac OS 8.5. This bug can cause previously registered servers to remain registered even after ShareWay IP has deregistered them. See the release notes for details.

The "Browse AFP Servers" menu item is grayed out

• You are probably not running Mac OS 8.5, which is required for this functionality.

A server shows up in the "Browse AFP Servers" list which I believe is no longer running

• There is a bug in the SLP plug-in which ships with Mac OS 8.5. This bug can cause previously registered servers to remain registered even after ShareWay IP has deregistered them. See the release notes for details.
  
  
• It's possible you are running the background version of ShareWay IP 2.0. Click on the server in the list to determine ShareWay's IP address, then check that machine to see if it's running the background version, as indicated in the ShareWay IP User's Guide.

A URL, as opposed to a server name, shows up in the "Browse AFP Servers" list

• An application other than ShareWay IP has registered an AFP server through SLP, however it has not used a URL of the form expected by AFP Engage!

AFP URL Processing

I registered AFP Engage! with Netscape, but when I quit and relaunch Netscape, it doesn't recognize AFP URLs.

• Netscape 3.0 and 3.0.1 have a bug such that they "forget" about AFP Engage! between sessions. That is, when you quit and relaunch Netscape 3.0 or 3.0.1, you will have to reregister AFP Engage! with Netscape. A workaround is covered in the Release Notes.

AFP Engage! tells me it successfully registered as an AFP helper, but my browser won't process AFP URLs.

• When processing AFP URLs in HTML documents, different combinations of browser type and OS version require AFP Engage! to either register with the browser to be used, or with Internet Config (or the Internet Control Panel for OS 8.5). The requirements are summarized in Table 1 below.
  
  

  	Mac OS 8.5	Mac OS Pre-8.5
  Netscape Navigator	with browser	with browser
  Microsoft Internet Explorer	as AFP helper app	either

Table 1 Registration Requirements

When first launched, or when "Register as AFP Helper" is chosen from the File menu, AFP Engage! attempts to register with whatever Web browser is running (if any) and with Internet Config or Mac OS 8.5's Internet Control Panel (if installed). AFP Engage! reports success if either registration was successful. Using Table 1 above, be sure that either 1) your Web browser is running, or 2) Internet Config (or the Internet Control Panel for OS 8.5) is installed, before registering AFP Engage!, so that the correct registration is performed.

AFP Engage! tells me there is no such volume on the server, but I know there is.

• The specified volume may have conflicting privileges with an already-mounted volume on the same server. Unmount mounted volumes and try again.

AFP Engage! says it can't find the file or folder.

• If any file or folder in the pathname contains a "/", it must be escaped as "%2F". In some cases, other characters, such as spaces, should be escaped as well. See Special Characters.

AFP URLs work over AppleTalk, but not over TCP/IP.

• The machine on which AFP Engage! is running must have a functioning TCP/IP connection.
  
  
• The server to which you're trying to connect must support AFP over TCP/IP. Versions of AppleShare prior to 5.0, all versions of Macintosh File Sharing, and most non-Apple AFP servers do not support AFP over TCP/IP directly. You can add TCP support to these servers through Open Door Networks' ShareWay IP product. If you are trying to access a non-Apple AFP server, consult the server's manufacturer to determine if its supports AFP over TCP/IP.

AFP Engage! is not listed as a helper app for my browser, even though it's been registered.

• Although AFP Engage! acts much like a helper app, it is technically an external protocol handler and thus is not listed in your browser's helper app window.

I click on an AFP URL but AFP Engage! tells me that a volume name may be required.

• Versions of the AppleShare Client prior to 3.7.2 require volume names in AFP URLs. Upgrade your AppleShare Client to the newest version.

When I try to use AFP URLs with my Web browser, they appear to begin with "file://".

• AFP Engage! has not registered with your browser. Launch AFP Engage! and choose "Register as AFP Helper" from the File menu. Be sure to reload the Web page.

Back to Table of Contents
Back to How AFP Engage! Works